home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
dskut
/
cross10.zip
/
CROSS.DOC
next >
Wrap
Text File
|
1980-01-01
|
5KB
|
134 lines
CROSS and UNCROSS 1.0 (c) 1989 by Craig Markwardt
Description: Splits large files into diskette-sized chunks.
Usage: CROSS [{/|-}{sSIZE|oOUTFILE|h|?}] [d:path]filename d:[outputpath]
UNCROSS [{/|-}{t|h|?}] [d:path]filename d:[outputpath]
OPTIONS:
sSIZE Forces output files to be SIZE bytes in size.
oOUTFILE Forces output file name to OUTFILE (don't include extension).
t Tests CROSSed file for integrity.
? or h Brings up quick help.
Synopsis: CROSS takes any sized file and chops it into smaller, disk-sized
files for floppy disk transfer. It allows for disk swapping and
hard disk operation. CROSS determines whether the output disk is
removable media or not. If it is removable, CROSS calculates the
size of the disk and then copies the data from the input file onto
the disk and includes a small (less than 50 bytes) header
describing the filename, attributes, creation dates, and a 16-bit
CRC. It automatically prompts for the next disk when needed. It
appends the extension ."xxx" where "xxx" is the chunk number. If
CROSS detects a hard disk as the output drive, then it
automatically writes chunks of 360k unless otherwise specified by
the s option. If you specify a size for the s option, CROSS will
create output files of that size in bytes. Specifying an output
name using the o option creates files with that name. However,
don't specify an extension for the o option since the chunk number
will replace it. Remember, don't leave spaces between the option
letter and its argument.
CROSS uses 50 bytes for each output chunk it processes for
header information and other stuff. It calculates and records a
16-bit CRC for each chunk during CROSSing for data verification.
UNCROSS assembles the original files from its disk-sized
chunks. It first checks the header to see if it was created with
a compatible version of CROSS. If it is compatible, then it
creates the output file on the designated disk. It then copies
the data from chunk to the output file and performs CRC data
checking. When it is finished with all of the chunks, it then
resets file attributes and creation dates. The t option is used
to test the integrity of CROSSed chunks.
Examples: CROSS myfile.dat A:
CROSSes myfile.dat to the A: drive and uses all free space on A:.
The output files will be named A:myfile.0, A:myfile.1, etc.
CROSS -s1200000 myfile.dat A:
Forces the output files to be 1.2 meg in size.
CROSS, UNCROSS Craig Markwardt page 2
CROSS /oYOURFILE myfile.dat B:
CROSSes myfile.dat to the B: drive with output files named
yourfile.0, yourfile.1, yourfile.2, etc. UNCROSSing will restore
the original filename of myfile.dat.
CROSS myfile.dat C:\TEMP
CROSSes myfile.dat to the hard drive directory \TEMP with a
default chunk size of 360K. Use the s option to change the
default size.
UNCROSS A:yourfile C:
UNCROSSes the file yourfile from the A: drive to the C: drive. As
in the example above, yourfile would be converted back to the
original filename myfile.dat.
UNCROSS /t A:yourfile
Tests integrity of A:yourfile chunks.
Bugs: CROSS and UNCROSS cannot handle wildcards.
You must have 78K free RAM to run CROSS or UNCROSS.
Currently, CRC checking/calculating is kind of slow, but future
releases will have table lookup CRC.
Remember, this program is in its first release, and there are
bound to be bugs a-crawling everywhere, especially on special
configurations. Please send all bug reports to the addresses
listed below.
Send all bug reports or suggestions to wboson@portia.stanford.edu on
Internet, or Jacob Brostoff in the Private Email conference on
Exec-PC, or to Jacob Brostoff at the Forecast Office (Milwaukee).
If you find CROSS and UNCROSS useful and can spare a small contribution, I
would appreciate any donation that you feel appropriate. Please contact
the above locations by Email if you're interested in making
contributions.
Craig Markwardt and Jacob Brostoff